[{"_1":2,"_605":-5,"_606":-5},"loaderData",{"_3":4,"_604":-5},"routes/topics.$name",[5,25,36,43,53,66,78,87,96,105,115,125,136,145,151,157,167,177,183,189,197,203,213,219,229,240,250,263,273,283,289,299,312,322,332,341,347,357,367,373,379,389,395,405,415,421,430,440,450,459,495,504,514,524,535,541,549,558,568,579,585,594],{"_6":7,"_8":9,"_10":11,"_12":13,"_18":19,"_21":22,"_23":24},"id","c1a00c374de9bc21379f2608c90dfad8b65e93310978670e9652838c17942edf","question","In Azure Cosmos DB, when working with stored procedures, triggers, or user-defined functions, what specific method can be utilized to log the execution steps or trace information?","answer","stored procedures, triggers, and user-defined functions are written on JavaScript.","options",[14,15,16,17],"Console.WriteLine()","Trace.Debug()","System.out.println()","console.log()","answerIndexes",[20],3,"hasCode",false,"topic","Cosmos DB",{"_6":26,"_8":27,"_10":28,"_12":29,"_18":34,"_21":22,"_23":24},"c6b5e4a19606c45e1a33ccaeb6b598d3160b3bac4c2fe764ddf64ef407aec706","You are designing an application that will use Azure Cosmos DB as its data store. The application will have several containers, each storing different types of data, but none of the containers are expected to have a high volume of read and write operations. You want to optimize costs while ensuring that all containers have enough throughput. Which of the following strategies would be the most cost-effective?","Shared throughput in Azure Cosmos DB is specified at the database level and then shared among all containers within the database. This is ideal for scenarios where you have multiple containers that do not require a high volume of operations and you want to optimize costs. \nDedicated throughput is specified at the container (not at dayabase level) level and would be more expensive for a scenario where the containers do not have a high volume of operations. \nShared throughput is not assigned at the container level but at the database level.",[30,31,32,33],"Assign dedicated throughput to each container individually, ensuring each has enough to handle its expected load.","Assign shared throughput at the database level, allowing all containers to draw from a common pool of throughput.","Assign dedicated throughput at the database level, ensuring the entire database has enough to handle its expected load.","Assign shared throughput to each container individually, allowing each to draw from its own pool of throughput.",[35],1,{"_6":37,"_8":38,"_10":39,"_12":40,"_18":41,"_21":42,"_23":24},"ed9cd4eb13f4baf914c37148b1263c7a5d062a4da47f9e7f3cfb6185661d486b","Given the following data:\n\n```json\n[\n {\n \"id\": \"6e9f51c1-6b45-440f-af5a-2abc96cd083d\",\n \"categoryName\": \"Sleeping Bags\",\n \"name\": \"Vareno Sleeping Bag (6') Turmeric\",\n \"price\": 120,\n \"closeout\": true,\n \"manufacturer\": {\n \"name\": \"Vareno\"\n },\n \"tags\": [{ \"name\": \"Color Group: Yellow\" }, { \"name\": \"Bag Shape: Mummy\" }]\n }\n]\n```\n\nWhat result this query will produce:\n\n```Cosmos DB\nSELECT {\n \"name\": p.name,\n \"sku\": p.sku,\n \"vendor\": p.manufacturer.name\n} AS product\nFROM products p\nWHERE p.sku = \"teapo-surfboard-72109\"\n```\n\n```jsonc\n[\n // Result here\n]\n```","\n\n```json\n[\n {\n \"product\": {\n \"name\": \"Teapo Surfboard (6'10\\\") Grape\",\n \"sku\": \"teapo-surfboard-72109\",\n \"vendor\": \"Taepo\"\n }\n }\n]\n```",[],[],true,{"_6":44,"_8":45,"_10":46,"_12":47,"_18":52,"_21":22,"_23":24},"6282f10bf0b671c80df751dad84317c07112276f15955295a5e7afccc182d014","What is the prerequisite for enabling service-managed failover in Azure Cosmos DB?","The service-managed failover feature requires your account to have two or more regions, as it needs a backup region to failover to if the primary region becomes unavailable.",[48,49,50,51],"Your account must have at least one region","Your account must have two or more regions","Your account must have multi-region writes enabled","Your account must be configured for manual failover",[35],{"_6":54,"_8":55,"_10":56,"_12":57,"_18":63,"_21":22,"_23":24},"be65cf74054bf6668eb9798891e6830f878a32af3dd57dea171665d9885e3a55","What operations can a stored procedure perform of document in Cosmos DB?","Stored procedures are capable of performing CRUD and query operations on any document in a collection.",[58,59,60,61,62],"Create","Read","Update","Delete","No operations allowed",[64,35,65,20],0,2,{"_6":67,"_8":68,"_10":69,"_12":70,"_18":76,"_21":22,"_23":24},"71585d333c355c47f7439d5e5bd8131e642dd2fb703394f69f31e1ee6c4da006","What is the correct syntax to select all properties from items in a Cosmos DB container?","Same as SQL. Note: The `SELECT *` syntax is only valid if FROM clause has declared exactly one alias.",[71,72,73,74,75],"`SELECT *`","`SELECT c.*`","`SELECT ALL`","`SELECT c.ALL`","`SELECT c FROM root AS c`",[64,35,77],4,{"_6":79,"_8":80,"_10":81,"_12":82,"_18":86,"_21":22,"_23":24},"0630920998328518d723d651ffda4938b586f5b835239f3507f4842e191f30e5","What is the role of pretriggers in Azure Cosmos DB?","Pretriggers in Azure Cosmos DB are executed before modifying a database item and they need to be specified for each database operation where they should execute.",[83,84,85],"Pretriggers are automatically executed for each database operation.","Pretriggers are executed before modifying a database item and must be specified for each database operation where you want them to execute.","Pretriggers are used to execute operations after modifying a database item.",[35],{"_6":88,"_8":89,"_10":90,"_12":91,"_18":95,"_21":22,"_23":24},"b2bee7eb9e6cc9b312c529ef8d276092c905541a955d99504cf896d1876451cf","What is the purpose of the lease container in the Azure Cosmos DB change feed processor?","The lease container acts as a state storage and coordinates processing the change feed across multiple workers.",[92,93,94],"It stores the data from which the change feed is generated.","It processes the change feed across multiple workers.","It acts as a state storage and coordinates processing the change feed across multiple workers.",[65],{"_6":97,"_8":98,"_10":99,"_12":100,"_18":104,"_21":22,"_23":24},"ea301ee58bf7803e7f68bdcddd515b7314fa88584f755776a6fa311fbc2bc83f","Which of the following would one use to validate properties of an item being created?","Pretriggers can be used to conform data before it's added to the container. \nPost-triggers run after an item is created. \nUser-defined functions run on existing data.",[101,102,103],"Pretrigger","Post-trigger","User-defined function",[64],{"_6":106,"_8":107,"_10":108,"_12":109,"_18":114,"_21":22,"_23":24},"d27652d745eaa19e4a9b206554806feb7b08c7b0033e866f0d1e87cc10d7f97b","What is the main advantage of using autoscale throughput in Azure Cosmos DB?","Autoscale automatically adjusts the amount of throughput based on the current workload.",[110,111,112,113],"It provides a fixed amount of throughput regardless of workload.","It automatically adjusts the amount of throughput based on the current workload.","It allows throughput to be shared among multiple containers.","It requires manual adjustment of throughput based on workload.",[35],{"_6":116,"_8":117,"_10":118,"_12":119,"_18":124,"_21":22,"_23":24},"f83ac022ad3563bc7d9e1993295d812949100ccbd6a5aa0dc173efc10eaa35c2","When executing a query in Azure Cosmos DB utilizing the Table API as follows:\n\n```Cosmos DB\nSELECT\nFROM Invoices i\nWHERE i.id =1\n```\n\nWhat kind of outcome can you anticipate from this query?","Cosmos DB internally stores data in a JSON-like format, regardless of the API used.",[120,121,122,123],"Data in an XML format","Data in a JSON format","An error due to incorrect syntax","A table structured in rows and columns",[35],{"_6":126,"_8":127,"_10":128,"_12":129,"_18":135,"_21":22,"_23":24},"100ced3515fd751a5cef80f6f3fe91636911626e90d6896dcc54a9c632c045a9","Your company is creating a social media platform with a feature to 'like' posts. It's more important to have high availability and throughput, and your application can handle some temporary inconsistencies, like the count of likes appearing out of order or slightly stale. What consistency level would be most suitable for this scenario?","Eventual consistency level prioritizes availability and throughput over immediate consistency.",[130,131,132,133,134],"Strong","Session","Bounded staleness","Consistent prefix","Eventual",[77],{"_6":137,"_8":138,"_10":139,"_12":140,"_18":144,"_21":22,"_23":24},"a3a4a4b48f8473a873fc06fe8bd344abfb2dca8c347c18593988611f16551862","When defining a stored procedure in the Azure portal input parameters are always sent as what type to the stored procedure?","When defining a stored procedure in Azure portal, input parameters are always sent as a string to the stored procedure.",[141,142,143],"String","Integer","Boolean",[64],{"_6":146,"_8":147,"_10":148,"_12":149,"_18":150,"_21":22,"_23":24},"e4c4be9ff739f0fc83e182f4967be1cefbe2fd83006e2d65058c67a8c5ea4229","Create a stored procedure that creates a document.\n\n```js\nvar createDocumentStoredProc = {\n id: \"createMyDocument\",\n // This stored procedure creates a new item in the Azure Cosmos container\n body: function createMyDocument(documentToCreate) {\n // Code here\n },\n};\n```","\n\n```js\nvar createDocumentStoredProc = {\n id: \"createMyDocument\",\n // This stored procedure creates a new item in the Azure Cosmos container\n body: function createMyDocument(documentToCreate) {\n var context = getContext();\n var collection = context.getCollection();\n\n // Async 'createDocument' operation, depends on JavaScript callbacks\n // returns true if creation was successful\n var accepted = collection.createDocument(\n collection.getSelfLink(),\n documentToCreate,\n // Callback function with error and created document parameters\n function (err, documentCreated) {\n // Handle or throw error inside the callback\n if (err) throw new Error(\"Error\" + err.message);\n // Return the id of the newly created document\n context.getResponse().setBody(documentCreated.id);\n }\n );\n\n // If the document creation was not accepted, return\n if (!accepted) return;\n },\n};\n```",[],[],{"_6":152,"_8":153,"_10":154,"_12":155,"_18":156,"_21":22,"_23":24},"3e60cfebbdb32f549ae50e855df8327d032654bbf82495fd034ec0e8df91c27e","Complete the following pre-trigger that adds timestampt to every new item:\n\n```js\nfunction validateToDoItemTimestamp() {\n /* Code here */\n\n // item to be created in the current operation\n var itemToCreate = /* Code here */;\n\n // validate properties\n if (!(\"timestamp\" in itemToCreate)) {\n var ts = new Date();\n itemToCreate[\"timestamp\"] = ts.getTime();\n }\n\n // update the item that will be created\n /* Code here */\n}\n```","\n\n```js\nfunction validateToDoItemTimestamp() {\n var context = getContext();\n var request = context.getRequest();\n\n // item to be created in the current operation\n var itemToCreate = request.getBody();\n\n // validate properties\n if (!(\"timestamp\" in itemToCreate)) {\n var ts = new Date();\n itemToCreate[\"timestamp\"] = ts.getTime();\n }\n\n // update the item that will be created\n request.setBody(itemToCreate);\n}\n```",[],[],{"_6":158,"_8":159,"_10":160,"_12":161,"_18":166,"_21":22,"_23":24},"2317700ead93cfaeaf916a32fa08d75003366d03945b8d52e47bf305a16cb268","You are developing an application that requires the efficient and rapid addition of a large number of items using Azure Cosmos DB. Which of the following practices can be employed to optimize performance for this use case?","Setting `EnableContentResponseOnWrite` to false for workloads with heavy create/write payloads and excluding unused paths from indexing can improve performance by eliminating the return of created or updated resources to the SDK and facilitating faster writes, respectively, benefiting write-heavy workloads.\n\nUsing `FeedIterator` can improve performance when reading multiple pages of query results, but it doesn't directly optimize write-heavy workloads. \nUsing `PartitionKey` for point read can reduce the Request Unit (RU) charge and improve performance for read-heavy workloads, but it doesn't directly optimize write-heavy workloads.",[162,163,164,165],"Set the `EnableContentResponseOnWrite` request option to false.","Use `FeedIterator` for iterating multiple pages of query results.","Exclude unused paths from indexing.","Use `PartitionKey` for point read.",[64,65],{"_6":168,"_8":169,"_10":170,"_12":171,"_18":176,"_21":22,"_23":24},"027f86863fa41c7ba20dd55b2f948c2226846e9b89db0aeecb1e8eba6eb8d9b2","You are designing an application that will use Azure Cosmos DB as its data store. The application will store data about customers and their orders. Each customer can have multiple orders, and you expect a high volume of read and write operations on the orders.\n\nYou want to ensure that the application can handle the expected load and that the data is distributed efficiently. You also want to ensure that the application can retrieve all orders for a specific customer as efficiently as possible.\n\nHow would you design the data model in Azure Cosmos DB to meet these requirements?","A container can hold items with different schemas as long as they share the same partition key. By storing customers and their orders in the same container and using the `customer ID` as the partition key, you can ensure that all orders for a specific customer are stored in the same partition. This makes it efficient to retrieve all orders for a specific customer. \nThe other options are incorrect because they do not efficiently distribute the data or allow for efficient retrieval of all orders for a specific customer.",[172,173,174,175],"Create separate databases for customers and orders, and use the `customer ID` as the partition key for the orders database.","Create a single container for both customers and orders, and use the `customer ID` as the partition key.","Create separate containers for customers and orders, and use the `customer ID` as the partition key for the orders container.","Create separate containers for customers and orders, with the `customer ID` as the partition key for the customers container and the `order ID` as the partition key for the orders container.",[35],{"_6":178,"_8":179,"_10":180,"_12":181,"_18":182,"_21":42,"_23":24},"0e064e9047b36f424d7dae65be817679dde8faa0be15b0ef913af905001198e0","You have to ensure the following query can be executed:\n\n```sql\nselect * from customers order by customername, city asc\n```\n\nYou have to define a policy for this:\n\n```jsonc\n{\n \"automatic\": true,\n \"indexingMode\": \"Consistent\",\n \"includedPaths\": [{ \"path\": \"/*\" }],\n \"excludedPaths\": []\n /* Code here */\n}\n```","Queries that have an `ORDER BY` clause with two or more properties require a composite index.\n\n```json\n{\n \"automatic\": true,\n \"indexingMode\": \"Consistent\",\n \"includedPaths\": [{ \"path\": \"/*\" }],\n \"excludedPaths\": [],\n \"compositeIndexes\": [\n [\n {\n \"path\": \"/city\",\n \"order\": \"ascending\"\n },\n {\n \"path\": \"/customername\",\n \"order\": \"descending\"\n }\n ]\n ]\n}\n```",[],[],{"_6":184,"_8":185,"_10":186,"_12":187,"_18":188,"_21":22,"_23":24},"fc7f7a0d6bc2e4e07df3b689a70fbdcf14b4256fa79b394d86507a9a0819f58c","Which of the following consistency levels offers the greatest throughput?","The eventual consistency level offers the greatest throughput at the cost of weaker consistency.",[130,131,132,133,134],[77],{"_6":190,"_8":191,"_10":192,"_12":193,"_18":196,"_21":22,"_23":24},"6466adaacb12287dd943ed3ac41ced6c14780edc7d732cc117b485f8e25252ed","Given the following query, which option correctly selects all properties from items in the container?\n\n```sql\nFROM c\nJOIN p IN c.phones\n```","`SELECT c.*`\nThe `SELECT *` syntax is only valid if the FROM clause has declared exactly one alias. In this case, the FROM clause has declared two aliases (`c` and `p`), so `SELECT *` is not valid. \nThe `SELECT p.*` syntax would select all properties from the items in the phones array \nThe `SELECT c.*, p.*` would select all properties from both the items in the container and the phones array. However, in this context, SELECT c.\\* is the correct answer because the question asks for all properties from items in the container.",[71,72,194,195],"`SELECT p.*`","`SELECT c.*, p.*`",[35],{"_6":198,"_8":199,"_10":200,"_12":201,"_18":202,"_21":42,"_23":24},"dbcf670e2e3f144ddca51ed32cb1b7e4c4a398d7e7f11a81fb97d5da9b329544","You aim to create a Cosmos DB client, a database, and finally a container using the Azure Cosmos DB NoSQL API. Your intention is to utilize this container to manage a collection of IoT device telemetry data. Implementing .NET for this task, you find that after running the following code snippet, errors are encountered and no elements are created as anticipated. Several discrepancies in the code prevent its successful execution. What corrections should you apply to address these issues?\n\n```cs\nusing Azure.CosmosDb;\n\nCosmosClient cosmosClient = new CosmosClient(\"https://myCosmosAccount.documents.core.windows.net:443/\", configuration[\"CosmosKey\"]);\n\nDatabase database = await cosmosClient.CreateDatabaseIfNotExistsAsync(\"db\");\n\nContainer container = await database.CreateContainerAsync(\n id: \"id\",\n partitionKeyPath: \"pk\",\n throughput: 200\n);\n```","\n\n```cs\nusing Microsoft.Azure.Cosmos;\n\nCosmosClient cosmosClient = new CosmosClient(\"https://mycosmosdbaccount.documents.azure.com:443/\", configuration[\"CosmosKey\"]);\n\nDatabase database = await cosmosClient.CreateDatabaseIfNotExistsAsync(\"dbName\");\n\nContainer container = await database.CreateContainerAsync(\n id: \"containerId\",\n partitionKeyPath: \"/pk\",\n throughput: 400\n);\n```\n\n- **Incorrect using** - should use `Microsoft.Azure.Cosmos`.\n\n- **Incorrect Cosmos DB account endpoint** - The endpoint used to initialize the CosmosClient object is incorrect. The provided endpoint URL contains `core.windows.net` instead of `documents.azure.com`.\n\n- **Incorrect database name** - should be between 3 and 63 chars, `db` is just 2.\n\n- **Incorrect container id** - should be between 3 and 63 chars, `id` is just 2.\n\n- **Incorrect partition key path** - The partition key path doesn't start with a `/`.\n\n- **Incorrect throughput value** - The throughput argument is set to 200, but minimum is 400 or higher.",[],[],{"_6":204,"_8":205,"_10":206,"_12":207,"_18":212,"_21":22,"_23":24},"657dac9763de9afba4870dadb9f9f68f3327e60ef523630be24db8041248c399","In Azure Cosmos DB, when dealing with a schema design that requires optimizing read operations and reducing the number of joins, what approach is commonly used?","Denormalizing is the process of restructuring a database to reduce redundancy and improve read performance. In Azure Cosmos DB, denormalizing can help in optimizing read operations by reducing the need for complex joins and aggregations. This approach can lead to faster query execution, especially in a distributed database system like Cosmos DB.",[208,209,210,211],"Normalizing","Sharding","Denormalizing","Partitioning",[65],{"_6":214,"_8":215,"_10":216,"_12":217,"_18":218,"_21":22,"_23":24},"e632583c647f21f7e3351faace65c4c1a979bcd7fa767f2fd590d5f8f6218669","What is the most suitable consistency level for a database solution that ensures sequential data writes are returned with no gaps, can process data using either its most recent or previous version, strives to minimize latency and negative impacts on data availability, and also keeps processing overhead as minimal as possible?","The bounded Staleness consistency level ensures that data writes are returned sequentially (no gaps). You have the flexibility to set up staleness, deciding the version of data to be returned, based on either the count of versions or the time elapsed. \nAll other options (except Eventual) also enabless gapless reads, but cannot configure staleness.",[130,131,132,133,134],[65],{"_6":220,"_8":221,"_10":222,"_12":223,"_18":228,"_21":22,"_23":24},"08c774e4712070bf926497a8ad4e701e0439799428525d5c85cac992dea059e2","When would you use the manual failover feature in Azure Cosmos DB?","Manual failover allows you to manually trigger a failover to a backup region, which is useful for testing your application's resilience to failures.",[224,225,226,227],"When you want to test your application's resilience","When you want to add a new region to your account","When you want to enable multi-region writes","When you want to create a new Azure Cosmos DB account",[64],{"_6":230,"_8":231,"_10":232,"_12":233,"_18":239,"_21":22,"_23":24},"008af6d967c6ec8111485988db35966a41aa0f7a9fc703e6c295c60e2fce126b","Your company has recently started using Azure Cosmos DB and hasn't made any adjustments to the consistency level. What delay should the company expect in data propagation between different regions?","Default consistency level is **Session**",[234,235,236,237,238],"No delay, data is immediately consistent across all regions.","Delay is limited to a specific number of operations or time interval.","Delay may occur but is contained within a single user's session.","Delay is possible and data might be read in the order of writes but a bit behind the latest.","Delay and out-of-order reads may occur, but the system will eventually become consistent.",[65],{"_6":241,"_8":242,"_10":243,"_12":244,"_18":249,"_21":22,"_23":24},"06cf1626ba05f3deabe75ed57d48a633651db9c3c48f81dfde0568c10c246713","You are working on an Azure-based application that utilizes Azure Cosmos DB for data storage. You've noticed scalability issues attributed to hot partitioning. What is the likely cause of this hot partitioning issue in Azure Cosmos DB?","Hot partitioning typically arises when there is an uneven distribution of requests or data across logical partitions. This imbalance prevents Azure Cosmos DB from scaling effectively. The ideal partition key should ensure a balanced distribution of both storage and throughput across partitions.",[245,246,247,248],"Executing queries that don't use the partition key","Running queries focused on a single partition key","Failing to set an indexing policy","Designing a partition key that leads to uneven request distribution",[20],{"_6":251,"_8":252,"_10":253,"_12":254,"_18":261,"_21":22,"_23":24},"63402f8093677ec8a11ac0f24c668a0e759c98d0ea00eae7595769d562829eb6","You are developing an application that needs to upload a large number of items into Azure Cosmos DB as quickly as possible. Which of the following practices could help improve performance?","Enabling Bulk support, utilizing `ThroughputProperties` for managing throughput, setting connectivity mode to `Direct`, and setting `EnableContentResponseOnWrite` to false can collectively enhance performance when efficiently handling large volumes of data in Azure Cosmos DB by optimizing high-volume write operations, balancing resource usage, and minimizing network and serialization costs. \nUsing Windows 64-bit host processing and a single instance of CosmoCLient can generally improve performance, but it doesn't specifically target scenarios where large volumes of data are being dumped into the database.",[255,256,257,258,259,260],"Enable Bulk support.","Use ThroughputProperties to manage throughput.","Use Direct mode for connectivity.","Use Windows 64-bit host processing.","Use single instance of CosmosClient.","Set the EnableContentResponseOnWrite request option to false.",[64,35,65,262],5,{"_6":264,"_8":265,"_10":266,"_12":267,"_18":272,"_21":22,"_23":24},"65d44013c77b6ce5df6448a3ecb9943ae1bdc2edeb89754d93a43c27945954a7","An e-commerce company is implementing a data migration operation on their Azure Cosmos DB database. The operation needs to be precisely controlled, allowing the engineering team to manually request the server for a set of changes, process them, and then request the next set. Which Change Feed interaction model best fits this use case?","The pull model offers extra control for specific use-cases, especially for data migration.",[268,269,270,271],"Pull Model","Push Model","Either Model","None of the Models",[64],{"_6":274,"_8":275,"_10":276,"_12":277,"_18":282,"_21":22,"_23":24},"d5d1c01165fd52025c93bde4609ce1b224afdd7ace1abc071f3b6baedaedc98b","Can you switch between dedicated and shared throughput in Azure Cosmos DB?","You cannot switch between dedicated and shared throughput once a container is created. If you want to change a container from shared to dedicated throughput, you must create a new container and copy the data to it.",[278,279,280,281],"Yes, you can switch at any time.","No, you cannot switch once a container is created.","Yes, but only within the first 24 hours of creating a container.","No, but you can increase the amount of dedicated throughput for a container.",[35],{"_6":284,"_8":285,"_10":286,"_12":287,"_18":288,"_21":42,"_23":24},"69350a1a8b265c91d2380ecd6d91b2d926d4f2d4784f0f728f7395f2cf574768","You are developing a system that needs to interact with Azure Cosmos DB. Your task is to write a piece of code that connects to a specific Cosmos DB instance and retrieves sales orders for a given account number, with a maximum item count of 1.\n\n```cs\nvar connectionString = \"\";\nvar dbName = \"\";\nvar containerName = \"\";\nvar partitionKey = \"Accounts\";\nvar throughputValue = 400;\nvar accountNumber = \"190823\";\n\n// Code here\n```","\n\n```cs\nvar connectionString = \"\";\nvar dbName = \"\";\nvar containerName = \"\";\nvar partitionKey = \"Accounts\";\nvar throughputValue = 400;\nvar accountNumber = \"190823\";\n\nvar cosmosClient = new CosmosClient(connectionString);\nDatabase database = await cosmosClient.CreateDatabaseIfNotExistsAsync(dbName);\nContainer container = await database.CreateContainerIfNotExistsAsync(id: , partitionKeyPath: $\"/{partitionKey}\", throughput: throughputValue);\nQueryDefinition query = new QueryDefinition(\n \"select * from sales s where s.AccountNumber = @AccountInput \")\n .WithParameter(\"@AccountInput\", accountNumber);\nFeedIterator resultSet = container.GetItemQueryIterator(\n query,\n requestOptions: new QueryRequestOptions()\n {\n PartitionKey = new PartitionKey(partitionKey),\n MaxItemCount = 1\n });\n```",[],[],{"_6":290,"_8":291,"_10":292,"_12":293,"_18":298,"_21":22,"_23":24},"bef662ba5c95db2b1666c9502ce4ff92cbec458d6738538975f12ac13df76e91","What is the primary reason for identifying access patterns in your solution when using Azure Cosmos DB?","[Identifying access patterns](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/model-partition-example#identify-the-main-access-patterns) helps design the data model to optimize application interactions, such as minimizing cross-partition queries or reducing request numbers through denormalization. \nAlthough cost can be influenced by data modeling, the main goal is performance optimization. \nThe choice of programming language is largely unrelated to data modeling. Access patterns don't dictate language choice. \nThe number of platform users is a business decision, not directly related to data modeling or access patterns.",[294,295,296,297],"To determine the cost of the solution","To ensure efficient data modeling","To choose the right programming language","To decide the number of users for the platform",[35],{"_6":300,"_8":301,"_10":302,"_12":303,"_18":311,"_21":22,"_23":24},"a6f0055236a2b99b8f4148b3e54790ad094b52e3b4764a52da73b39adf74f3c3","Which of the following statements about Time to Live (TTL) in Azure Cosmos DB are true? Select all that apply.","Even after TTL has expired, if the container is overloaded with requests and there aren't enough Request Units available, the data deletion is delayed until there are enough resources. \nItems are removed after specific time period, since the time they were **last modified**.",[304,305,306,307,308,309,310],"TTL can be set at the container level and can be overridden on a per-item basis.","TTL can be set only at item level.","When TTL has expired, if the container is overloaded with requests, data is immediately deleted.","Items with TTL set to \"-1\" don't expire by default.","If TTL is not set on a container, then the TTL on an item in this container has no effect.","If a container's TTL is null or missing, items without a specific TTL will not expire, while others adhere to their own TTL.","TTL is used for automatically deleting items after a certain period, based on their creation time.",[64,20,77],{"_6":313,"_8":314,"_10":315,"_12":316,"_18":321,"_21":22,"_23":24},"a948fed2cf75370a65e9b9bbb3b049e8783bdfa6136b281e3684e9833ee3ff1c","You're running a global highly available e-commerce application with Azure Cosmos DB, where updates to product inventory are made concurrently across multiple regions. However, you've noticed that sometimes inventory data gets out of sync across different regions. To ensure consistency in inventory data, what feature can you use in Azure Cosmos DB?","Setting up a conflict resolution policy helps manage conflicts that arise from concurrent writes across different regions, ensuring data consistency across regions. \nThe other options are related to performance, consistency levels, and write capabilities, but they don't directly address data conflicts arising from concurrent writes. \nDisabling multi-region writes could potentially avoid conflicts, but it would also negate the benefits of having a globally distributed application, like reduced latency for writes in different regions.",[317,318,319,320],"Increase Request Units (RUs)","Implement strong consistency level","Disable multi-region writes","Set up a conflict resolution policy",[20],{"_6":323,"_8":324,"_10":325,"_12":326,"_18":331,"_21":22,"_23":24},"0b1493b1a80f2ab0ea14507593289a239f3477cf8729c19b6cf14384a453c7c2","Your organization has deployed a multi-region Azure Cosmos DB database to ensure high availability. Each region can simultaneously read from and write to the database. There is a chance that the same document is updated concurrently in different regions, potentially leading to conflicts. To handle this, you've decided to use the automatic conflict resolution policy provided by Azure Cosmos DB. Based on your understanding of this policy, which strategy best describes how Azure Cosmos DB would resolve these conflicts?","Last Writer Wins",[327,328,329,330],"The update from the region that first modified the document is always retained.","The update from a randomly selected region is retained.","The update from the region that last modified the document is retained.","All updates from all regions are retained in some manner.",[65],{"_6":333,"_8":334,"_10":335,"_12":336,"_18":340,"_21":22,"_23":24},"b4582ee3bf32568585e992f5066ad8b833a5d30e7b75422cd54987a42003b8f4","What is the maximum amount of data a logical partition in Azure Cosmos DB can store?","20 GB",[337,335,338,339],"10 GB","50 GB","Unlimited",[35],{"_6":342,"_8":343,"_10":344,"_12":345,"_18":346,"_21":22,"_23":24},"413f0ba0c80968281c56895e71b1d14286a2dafe4b8d2af6d740a3ca0e7b4118","Your company is building a workflow management system where sequences of tasks are processed. It's crucial that these tasks are processed in the order they were written, even if it means reading data a bit behind the latest. What consistency level would be most suitable for this scenario?","Consistent prefix level ensures that the sequence of operations is preserved.",[130,131,132,133,134],[20],{"_6":348,"_8":349,"_10":350,"_12":351,"_18":356,"_21":22,"_23":24},"ca9288a50ac468f69d88665e555a99239b171d9ef3358ad5bfa144dff6b50266","Your application is experiencing latency issues when connecting to Azure Cosmos DB. Which of the following could be a potential cause and how would you address it?","Running your application in the same Azure region as your Azure Cosmos DB account and using Direct mode for connectivity can significantly reduce latency, optimizing the performance of your application.\n\nWhile using the latest version of the Azure Cosmos DB SDK can generally improve performance, it doesn't specifically target latency issues. \nUsing a single instance of CosmosClient for the lifetime of your application is a best practice for better performance and resource utilization, so it's unlikely to be the cause of latency issues.",[352,353,354,355],"The application is not using the latest version of the Azure Cosmos DB SDK.","The application is running in a different Azure region than your Azure Cosmos DB account.","The application is using a single instance of CosmosClient for the lifetime of the application.","The application is using Gateway mode for connectivity.",[35,20],{"_6":358,"_8":359,"_10":360,"_12":361,"_18":366,"_21":22,"_23":24},"dd30848feacd055ac21712f818b16243f4cc2814ec581cf80da0c9591267cdad","What is the role of a partition key in Azure Cosmos DB?","The partition key helps Azure Cosmos DB distribute the data efficiently across partitions. The value of this property is then used to route data to the appropriate partition to be written, updated, or deleted.",[362,363,364,365],"It helps to distribute data efficiently across partitions.","It is used to manage the Azure Cosmos DB account.","It is used to create a unique DNS name for the account.","It is used to group containers into a database.",[64],{"_6":368,"_8":369,"_10":370,"_12":371,"_18":372,"_21":42,"_23":24},"fc392d2c45d40ff05b1df6cbda370b7f130f06755b22c606c8c9a868f12e0c54","You are a software developer tasked with creating a C# utility that interacts with Azure Cosmos DB. Your script should establish a connection, create a database and a container if they don't exist, and finally create an item in the container. Use placeholders like `\"\"`, `\"\"`, `\"\"`.\n\n```cs\n// Code here\n```","\n\n```cs\nvar cosmosClient = new CosmosClient(\"\");\n\n// Create a database\nvar database = await cosmosClient.CreateDatabaseIfNotExistsAsync(\"\");\n\n// Create a container\nvar container = await database.CreateContainerIfNotExistsAsync(\"\", \"/mypartitionkey\");\n\n// Create an item\ndynamic testItem = new\n{\n id = \"1\",\n mypartitionkey = \"mypartitionvalue\",\n description = \"mydescription\"\n};\nawait container.CreateItemAsync(testItem, new PartitionKey(testItem.mypartitionkey));\n```",[],[],{"_6":374,"_8":375,"_10":376,"_12":377,"_18":378,"_21":22,"_23":24},"8fafc546846b2d9045cf908753f314c6dde0d4170740530d1d30460533536b23","Your company is developing a new online multiplayer game. The game includes a feature that shows a global leaderboard to players. The leaderboard doesn't have to be up-to-the-minute for each player, but any lag should be within a defined limit. What consistency level would be most suitable for this scenario?","The Bounded staleness consistency level allows for some lag in data propagation but within a defined limit.",[130,131,132,133,134],[65],{"_6":380,"_8":381,"_10":382,"_12":383,"_18":388,"_21":22,"_23":24},"07e2e6abd188dd5f5d9897ce03155a39da78a49fe8c2653859797e3de1cc48b1","What is the purpose of denormalization in the context of Azure Cosmos DB data modeling?","[Denormalization in Azure Cosmos DB data modeling](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/model-partition-example#v2-introducing-denormalization-to-optimize-read-queries) is used to optimize read queries. By storing related data together (denormalizing), you can retrieve all the data you need in a single query, reducing the need for multiple queries and improving performance. \nDenormalization doesn't aim to reduce the number of containers, increase the number of request units consumed, or add more users to the platform; it's a strategy to optimize read operations by organizing data efficiently within containers.",[384,385,386,387],"To reduce the number of containers","To optimize read queries","To increase the number of request units consumed","To add more users to the platform",[35],{"_6":390,"_8":391,"_10":392,"_12":393,"_18":394,"_21":22,"_23":24},"c97d9544857f9ff7731cc8f134e7524659db8562355f90acb19dbdb8b27ff2fb","Your company is creating a shopping platform where users interact with their own shopping carts. A user's actions should be immediately consistent within their session, but it doesn't have to be strongly consistent with other users' sessions. What consistency level would be most suitable for this scenario?","Session consistency level ensures that within a single session.",[130,131,132,133,134],[35],{"_6":396,"_8":397,"_10":398,"_12":399,"_18":404,"_21":22,"_23":24},"9f53c1e3bffbd8c0967309b5f65a9c7ba204bc490bcce98be1f138839d28d985","What is the main characteristic of shared throughput in Azure Cosmos DB?","Shared throughput in Azure Cosmos DB is specified at the database level and then shared with up to 25 containers within the database. The other options are incorrect because they describe characteristics of dedicated throughput, not shared throughput.",[400,401,402,403],"It is exclusively reserved for a single container.","It is specified at the database level and shared with up to 25 containers.","It automatically adjusts based on the current workload.","It is a fixed amount of throughput.",[35],{"_6":406,"_8":407,"_10":408,"_12":409,"_18":414,"_21":22,"_23":24},"944ead406fd807c9e68eb876c4013f6ac23103c285c6550af197b5219882d485","Which of the following tools can you use to create and execute triggers, stored procedures, and UDFs in Azure Cosmos DB?","The Azure Portal is one of the tools that allow you to create and execute triggers, stored procedures, and UDFs in Azure Cosmos DB. The other options listed are not directly used for this specific purpose within Azure Cosmos DB.",[410,411,412,413],"Visual Studio Code","Azure Portal","SQL Server Management Studio","Azure DevOps",[35],{"_6":416,"_8":417,"_10":418,"_12":419,"_18":420,"_21":22,"_23":24},"5e702c3b76de7a9bb43c375cd735cec1451e43cfa7211d9220c513bea9fd9f5e","Your company operates a financial application which handles sensitive transactions. It's critical that all operations are immediately consistent across all regions, even if it might impact performance. What consistency level would be most suitable for this scenario?","Strong consistency level ensures immediate consistency across all regions.",[130,131,132,133,134],[64],{"_6":422,"_8":423,"_10":424,"_12":425,"_18":429,"_21":22,"_23":24},"f891252d14d8b57e5a07d59540685803847b38e7e408573a3a976e55825c681e","What is the maximum throughput amount a physical partition in Azure Cosmos DB can have?","10,000 RU/s",[426,427,424,428],"1,000 RU/s","5,000 RU/s","20,000 RU/s",[65],{"_6":431,"_8":432,"_10":11,"_12":433,"_18":439,"_21":22,"_23":24},"d6dc222eeb6d7ec61dd10b11a1c3c87248386d0c22d619124c20100ebdbb0b44","What language should you use if you want to create a new user-defined function, stored procedure, or trigger?",[434,435,436,437,438],"JSON","JavaScript","C#","XML","YAML",[35],{"_6":441,"_8":442,"_10":443,"_12":444,"_18":449,"_21":22,"_23":24},"95f5b1c712a1e92387a452704fb9e9470eb5de77f75a887d49eb85cddc7de0e2","How to set Time-To-Live property of `ContainerProperties` to be 1 hour?","Property is `DefaultTimeToLive`, unit is _seconds_,",[445,446,447,448],"`DefaultTimeToLive = 60`","`DefaultTimeToLive = 3600`","`TTL = 60`","`TTL = 3600`",[35],{"_6":451,"_8":452,"_10":118,"_12":453,"_18":458,"_21":22,"_23":24},"56e1e515269eb500cf5996fe79fd63d414479d210b0266c1dd5bd6d35f17c2bf","Which of the following best describes the format of data returned by a Cosmos DB query when using the PostgreSQL API?",[454,455,456,457],"XML, since XML is a widely used format for data interchange.","Tabular data, since the PostgreSQL API transforms the data to resemble traditional SQL results.","JSON, because Cosmos DB internally stores data in a JSON-like format, regardless of the API used.","Binary data, encoded in a PostgreSQL-specific format.",[65],{"_6":460,"_8":461,"_10":462,"_12":463,"_18":486,"_21":22,"_23":24},"d9bad2c486895146611c9f0a06dc504233ed1e62d132f9e450f36dfcf3907f14","Given the following statements about Azure Cosmos DB's Change Feed, identify which ones are true:","\n\nThe retention time depends on the configured time-to-live of the items and the change feed retention period set on the container, by default it's 7 days. \nChange Feed is used in scenarios that require triggering a function or a logic app, real-time processing, or distributed database updates. \nIn the change feed, order is guaranteed within each logical partition key value, but not across them.",[464,465,466,467,468,469,470,471,472,473,474,475,476,477,478,479,480,481,482,483,484,485],"Change Feed in Azure Cosmos DB is automatically enabled upon creation of a container.","The Change Feed presents changes to a container in a chronological sequence.","Change Feed natively displays all modifications, including inserts, updates, and deletions.","There is only one interaction model with Change Feed, which is the push model.","A soft-delete pattern is supported in Azure Cosmos DB where a \"deleted\" attribute can be appended to items intended for deletion.","In the push model, the Change Feed processor independently dispatches tasks to a client.","Change Feed functionality is available across all API models in Azure Cosmos DB.","The pull model in Change Feed allows for manual checkpointing and control over processing speed.","Items can have a time-to-live (TTL) value attached for automatic deletion.","Change Feed functionality is limited to the SQL (Core) API in Azure Cosmos DB.","In the push model, the Change Feed processor requires manual intervention to dispatch tasks to a client.","Change Feed shows all inserts and updates, excluding deletions.","The Change Feed feature isn't compatible with Azure Cosmos DB's Table and PostgreSQL APIs.","Change Feed doesn't have a provision for distributing processing tasks across multiple instances.","The Change Feed feature is an add-on and comes with an additional cost.","Change Feed allows microservices to independently react to data changes.","Change Feed supports reading changes from a specific partition key.","The Change Feed retains the changes indefinitely until they are consumed.","Change Feed can be used to implement event sourcing patterns where the stream of events in Change Feed forms the source of truth and can be used to materialize the application’s state.","Change Feed cannot be used in scenarios that require triggering a function or a logic app, real-time processing, or distributed database updates.","With Change Feed, you can create low-latency, real-time data processing solutions.","Change feed guarantees order across the partition key values.",[64,35,77,262,487,488,489,490,491,492,493,494],7,8,11,12,15,16,18,20,{"_6":496,"_8":497,"_10":498,"_12":499,"_18":503,"_21":22,"_23":24},"950bf4a142b3bc978764c662b46a758aab97c25a619f1ebc65ad9b8465bfa3d7","How many free tier Azure Cosmos DB accounts can you have per Azure subscription?","You can have up to one free tier Azure Cosmos DB account per Azure subscription.",[500,339,501,502],"Two","One","None",[65],{"_6":505,"_8":506,"_10":507,"_12":508,"_18":513,"_21":22,"_23":24},"22ccdee5e660b4f6b069a996448997aaca548e5a7cd5fe1d088d37643d98b294","You are designing an application that will use Azure Cosmos DB as its data store. The application will have a high volume of read and write operations. You want to ensure that each container in your database can handle the expected load independently. How should you configure the throughput?","Dedicated throughput in Azure Cosmos DB is specified at the container level, meaning each container has its own amount of throughput that it can use independently of other containers. \nShared throughput is specified at the database level (not at container level) and shared among containers, not at the individual database level. \nDedicated throughput is not assigned at the database level but at the container level.",[509,510,511,512],"Use shared throughput and create a separate database for each container.","Use dedicated throughput and assign it to each container individually.","Use shared throughput and assign it to each container individually.","Use dedicated throughput and assign it at the database level.",[35],{"_6":515,"_8":516,"_10":517,"_12":518,"_18":523,"_21":22,"_23":24},"8736ca264c98058e3a7eae1c562f4b8ac956058703bdfe8b6bf62d5d1d8d8dab","What is the relationship between Azure Cosmos DB and Azure Resource Group?","To begin using Azure Cosmos DB, you need to create an Azure Cosmos DB account in an Azure Resource Group in your subscription.",[519,520,521,522],"Azure Cosmos DB is a type of Azure Resource Group.","Azure Resource Group is a type of Azure Cosmos DB.","Azure Cosmos DB account is created in an Azure Resource Group.","Azure Resource Group is created in an Azure Cosmos DB account.",[65],{"_6":525,"_8":526,"_10":527,"_12":528,"_18":534,"_21":22,"_23":24},"12146b94e15e8a72a71c309c6eb1aa0706d7745bee804ac40ba5a204bea4df3a","You are working on a project that involves storing large amounts of data in Azure Cosmos DB using the SQL API. The data consists of user profiles, each with a variety of attributes. During the design phase, you realize that no single attribute is suitable for partitioning, as they either appear too frequently or not frequently enough to distribute the workload evenly across partitions. Which of the following strategies could you use to create a synthetic partition key that ensures even distribution of workloads?","\n\n- Concatenating multiple common properties, followed by a random number, would create a synthetic partition key that is likely to distribute data more evenly across partitions. The random number ensures that the key is unique and helps in distributing the workload.\n- Appending a timestamp to the user's country of residence would also create a synthetic partition key that can distribute data more evenly. The timestamp ensures that even if many users are from the same country, their data will be spread across multiple partitions.\n- Using the user's email address as it is unique would not necessarily distribute the workload evenly, especially if the application has operations that need to query or update multiple documents that can't be guaranteed to be in the same partition.\n- Using the user's age would not be a good choice for partitioning, as it could lead to hot partitions. Age groups like 20-30 or 30-40 could have more data, leading to uneven distribution.\n- Using the user's membership status could also lead to hot partitions if one membership type is significantly more common than others.",[529,530,531,532,533],"Concatenating multiple common properties, followed by a random number","Using the user's email address as it is unique","Appending a timestamp to the user's country of residence","Using the user's age as the partition key","Using the user's membership status (e.g., Free, Premium, VIP)",[64,65],{"_6":536,"_8":537,"_10":538,"_12":539,"_18":540,"_21":22,"_23":24},"230bc71de5345323b92751879247461b7ffd2b9a3fbfb3e5ec9124af03e43f23","Given the following data:\n\n```json\n[\n {\n \"id\": \"6e9f51c1-6b45-440f-af5a-2abc96cd083d\",\n \"categoryName\": \"Sleeping Bags\",\n \"name\": \"Vareno Sleeping Bag (6') Turmeric\",\n \"price\": 120,\n \"closeout\": true,\n \"manufacturer\": {\n \"name\": \"Vareno\"\n },\n \"tags\": [{ \"name\": \"Color Group: Yellow\" }, { \"name\": \"Bag Shape: Mummy\" }]\n }\n]\n```\n\nWrite a query that will return this result, filtering by `teapo-surfboard-72109`:\n\n```json\n[\n {\n \"name\": \"Teapo Surfboard (6'10\\\") Grape\",\n \"sku\": \"teapo-surfboard-72109\",\n \"vendor\": \"Taepo\"\n }\n]\n```\n\n```sql\n-- Code here\n```","\n\n```sql\nSELECT VALUE {\n \"name\": p.name,\n \"sku\": p.sku,\n \"vendor\": p.manufacturer.name\n}\nFROM products p\nWHERE p.sku = \"teapo-surfboard-72109\"\n```",[],[],{"_6":542,"_8":543,"_10":544,"_12":545,"_18":548,"_21":22,"_23":24},"a50e86f1de8263afb08454b65953c83b96f73e5504225f5c149eb8c8af5a7359","You are developing an application with a read-heavy workload using Azure Cosmos DB. Which of the following practices could help improve performance?","Utilizing `PartitionKey` for point read can reduce Request Unit (RU) charges and enhance performance, particularly for read-heavy workloads, while employing `FeedIterator` can improve performance when handling multiple pages of query results, a common scenario in read-heavy workloads.\n\nSetting `EnableContentResponseOnWrite` to false can improve performance for write-heavy workloads, but it doesn't directly optimize read-heavy workloads. \nIncreasing the size of your documents can actually increase the Request Unit (RU) charge and potentially lead to more errors, so it's not a good practice for optimizing performance.",[165,162,546,547],"Use `FeedIterator` for iteratin multiple pages of query results.","Increase the size of your documents.",[64,65],{"_6":550,"_8":551,"_10":552,"_12":553,"_18":557,"_21":22,"_23":24},"bf3a9458915b9b2132334389ab60fc7b7e1329129fc43de4efc544417b25acbe","What are request units (RUs) in Azure Cosmos DB?","RUs represent the normalized cost of all database operations in Azure Cosmos DB, including writes, point reads, and queries.",[554,555,556],"A unit of measurement used to express the cost of all database operations in Azure Cosmos DB.","A unit of time used to measure the duration of database operations.","A unit of storage used to measure the amount of data stored in Azure Cosmos DB.",[64],{"_6":559,"_8":560,"_10":561,"_12":562,"_18":567,"_21":22,"_23":24},"5cf392ea48b02b532bf5d6c341826115506aeae1beab254c7bc101a77c0dbc5e","What is the main characteristic of Azure Cosmos DB containers regarding data schemas?","Containers in Azure Cosmos DB are schema-agnostic, meaning items within a container can have arbitrary schemas or different entities so long as they share the same partition key.",[563,564,565,566],"Containers require a strict schema for all items.","Containers are schema-agnostic.","Containers only support JSON schema.","Containers do not support any schema.",[35],{"_6":569,"_8":570,"_10":571,"_12":572,"_18":578,"_21":22,"_23":24},"5c7fa1d0371a61734f32d63b7eadab476ad0ac69ae7ace8b0ee384b16622736a","Your organization is planning to migrate a NoSQL database to Azure Cosmos DB and requires an API that can handle flexible document structures and operate using the BSON format. Which API within Azure Cosmos DB would best meet these requirements?","In the context of Azure Cosmos DB, the BSON (Binary JSON) format is specifically associated with the MongoDB API.",[573,574,575,576,577],"SQL API","Table API","Gremlin API","Cassandra API","MongoDB API",[77],{"_6":580,"_8":581,"_10":582,"_12":583,"_18":584,"_21":22,"_23":24},"6538b02d146a44bd7708c1889c32bc86b8799adb966451bf23e71a4abab135a2","A financial technology company is developing a real-time fraud detection system using Azure Cosmos DB. The system needs to react instantaneously to changes in the database, with minimal latency. Which Change Feed interaction model best fits this use case?","In the push model, the change feed processor automatically sends work to a client.",[268,269,270,271],[35],{"_6":586,"_8":587,"_10":588,"_12":589,"_18":593,"_21":22,"_23":24},"1c587bf05bff788974510b9eed5fcfe946225033fcdbc71d474e2051376c9466","What is the purpose of the context object in a stored procedure in Azure Cosmos DB?","The context object in a stored procedure provides access to all operations that can be performed in Azure Cosmos DB, and access to the request and response objects.",[590,591,592],"It provides access to the database schema and metadata.","It allows for the creation of new collections within the database.","It provides access to all operations that can be performed in Azure Cosmos DB, and access to the request and response objects.",[65],{"_6":595,"_8":596,"_10":597,"_12":598,"_18":603,"_21":22,"_23":24},"698b72ccef27c6ff5e70100bc18f15df7b66f2519210e6cb9fd63e5c39b2e800","How to retain the change feed in Azure Cosmos DB until the data is deleted? What should be the value of TTL (Time to Live) property?","If the TTL property is set on an item to -1, the change feed will remain if the data is not deleted.",[599,600,601,602],"null","-1","0","1",[35],"root","actionData","errors"]

AZ-204 Quiz

← Back to Topics